##[group]The deploy tool's tests
npm run test:deploy
##[endgroup]
shell: bash -e /home/runner/_temp/18dfc11da8948791.sh

> test:deploy
> node --test "scripts/deploy/*.test.mjs"

error: no matching package named `base64` found
location searched: crates.io index
required by package `g1t-api v0.1.0 (/home/runner/work/repo/apps/api)`
note: offline mode (via `--offline`) can sometimes cause surprising resolution failures
help: if this error is too confusing you may wish to retry without `--offline`
✔ the manifest matches every wrangler config in the repository (21.483078ms)
✔ every wrangler.jsonc is found, and only checked-in ones (64.105005ms)
✔ problems are found: an unlisted config, a later-stage binding, a wrong database, an unnamed KV (22.615839ms)
✔ stages follow bindings: nothing binds to a unit that ships after it (0.682251ms)
✔ Rust workers build with the shared script and the same wasm-opt level (0.60347ms)
✔ shared crates and packages are read from workspace metadata (0.32523ms)
✔ the runner's image is built from the runner crate and what it uses, on the base its lock names (0.47076ms)
✔ services/runner/base.json records the base its folder builds (6.709026ms)
✔ an image's hash ignores line endings, and its tags say what they are (104.439279ms)
✔ only the lockfile entries the runner is built from name its image (0.5278ms)
✔ the runner's deploy config names its image by reference, beside its wrangler.jsonc (62.741254ms)
✔ the registry is asked for an image's manifest, without Docker (0.97702ms)
✔ a push counts only when it ends with a digest, and is tried again (0.630481ms)
✔ a static Linux binary is told from a dynamic one (0.6966ms)
﹣ path dependencies agree with Cargo's own resolved graph (1714.762402ms) # cargo metadata could not resolve offline
✔ every import that leaves a unit's folder is covered by its dependencies or inputs (95.942552ms)
✔ a shared crate's change reaches every unit built from it, and no other (0.779531ms)
✔ a shared package's change reaches what imports it (0.21982ms)
✔ a crate's tests, benches and examples deploy nothing (0.984991ms)
✔ a Rust file compiled only for tests is found from what declares it (2.842252ms)
✔ this repository's test-only sources are read from git (609.79264ms)
✔ decide: a change only to tests deploys nothing (1.250581ms)
✔ own folders, declared inputs and root files (1.004861ms)
✔ a Cargo.lock change reaches only crates that use what changed (0.41301ms)
✔ a package-lock change reaches through workspace links (0.50885ms)
✔ decide: changed units deploy, others wait, unknown ones deploy (0.23823ms)
✔ decide: --force deploys unchanged units; a commit missing from history deploys (0.685581ms)
✔ decide: Cargo.lock counts only where it reaches (0.51035ms)
✔ decide: the runner's image rebuilds only when what it is built from changed (0.21116ms)
✔ the plan as data: migrations, and each stage's units in jobs that share a build (1.144001ms)
✔ units are picked by short name, folder or Worker name (0.51924ms)
✔ a CI job installs only what its units need (0.927631ms)
✔ a deploy is annotated with its commit, and read back (0.37898ms)
✔ the live commit: the live version's, looking through secret changes (0.30409ms)
✔ Wrangler's output: pending migrations and the version a deploy made (0.34635ms)
✔ the API's answers: the live commit as Wrangler's would give it (0.95477ms)
✔ the API's answers: a Worker never deployed, and a refusal, never throw (502.526398ms)
✔ the API is used only with the token Wrangler would be given (1.248291ms)
✔ pending migrations: the folder's files less the names in d1_migrations (1.236141ms)
✔ the pool runs everything, no more than its limit at once (14.497983ms)
✔ self-hosting builds every Rust service the manifest says it runs (0.37016ms)
✔ docs/SELF_HOSTING.md's table names every unit (0.28649ms)
✔ resolveStack works on a manifest with no workspace crates or packages (6.714616ms)
✔ decide: a commit older than what runs is never deployed by accident, even forced; --rollback means it (0.1776ms)
✔ a deploy by hand reports to the repository on g1t, and a workflow's does not (1.393501ms)
✔ webhooks: the hourly purge deletes old deliveries by time (3.103183ms)
✔ billing: this month's users are read from an index, not the ledger (34.151579ms)
✔ events: a repository's events of one type, newest first, page by page (1.811122ms)
✔ actions: a self-hosted runner's poll finds queued jobs by namespace, whatever its case (7.223166ms)
✔ chat: a channel's messages and a thread's replies, newest first, page by page (0.771851ms)
✔ chat: the sidebar's unread messages are read from each channel's index, after the last read (0.57935ms)
scheduler: g1t-webhooks (* * * * *) is still running from the last time; skipped
scheduler: g1t-webhooks (* * * * *): 200 {"outcome":"exception"}
✔ fields read numbers, ranges, lists and steps (1.340541ms)
✔ the services' crons match when hosted g1t's would fire (1.399931ms)
✔ what is due is each matching cron of each service (0.30396ms)
✔ a run asks Wrangler for the handler, and a slow one is not doubled (75.619514ms)
✔ a deploy is announced to status.g1t.sh with the token, and without one nothing is sent (34.64867ms)
✔ an announcement that fails is a warning, never a failed deploy (0.756761ms)
✔ the stages run inside the window: started before, finished after, even when they throw; a dry run says nothing (51.261114ms)
✔ deploy.mjs announces every deploy, and the workflow passes it the token (0.775041ms)
ℹ tests 59
ℹ suites 0
ℹ pass 58
ℹ fail 0
ℹ cancelled 0
ℹ skipped 1
ℹ todo 0
ℹ duration_ms 3870.076169
